Network facsimile apparatus and transmission method

ABSTRACT

A communication apparatus is connected to a terminal apparatus via a network. The communication apparatus includes an e-mail receiver that performs an e-mail reception via the network. A file generator generates an HTML file for a web page indicating a result of the e-mail reception performed by the e-mail receiver. A storage stores the HTML file generated by the file generator. A web server transmits the HTML file to the terminal apparatus via the network so that the web page is displayed at the terminal apparatus.

This application is a divisional of U.S. patent application Ser. No.09/314,958, filed on May 20, 1999, now U.S. Pat. No. 6,956,663 entitled“Network Facsimile Apparatus and Transmission Method” in the name ofJunichi IIDA, the disclosure of which is expressly incorporated byreference herein in its entirety.

FIELD OF THE INVENTION

The present invention relates to a network facsimile apparatus andtransmission method capable of performing transmission and reception offacsimile data and e-mail data connecting to a PSTN and a network suchas the internet or LAN.

DESCRIPTION OF THE RELATED ART

Recently, it has been performed to connect a personal computer, workstation, FAX server or the like to a network in order to transmit andreceive an e-mail and facsimile and to browse homepages.

FIG. 1 illustrates a system structure in which facsimile transmissionand reception is performed using a FAX server. The reception operationat a client machine (personal computer) will be described next. FAXmodem 1001 receives a call from the PSTN and reads out image data totransmit to FAX server 1002. FAX server software operating at FAX server1002 receives the image data. The FAX server stores the image data as animage data file at file server 1003 through the network. At this point,the storage of facsimile received data is finished.

To fetch the received image data into client machine 1004, a user startsa dedicated application at client machine 1004 and reads out the imagedata from file server 1003 through the network.

Further, a method of reusing facsimile received data by combining aninternet FAX and a WWW server has been recently proposed. The methodutilizes the function of the internet FAX which converts data receivedfrom the PSTN into an e-mail.

FIG. 2 illustrates a system structure in which facsimile transmissionand reception is performed using an internet FAX and a WWW server. Thereception operation at the client machine will be described.

Image data received at internet FAX 1101 via the PSTN is attached to ane-mail at internet FAX 1101 and is transmitted to WWW server 1103 as anattached file of e-mail.

The e-mail with the attached file transferred from internet FAX 1101 isreceived at e-mail server 1102 via a network. The e-mail with theattached file received at e-mail server 1102 is transferred to WWWserver 1103 that is a destination again via the network.

WWW server 1103 stores the attached file of e-mail as image data to linkto a homepage for facsimile reception. The storage of facsimile receiveddata is finished at this point.

In order to fetch received data into client machine 1104, a user startsa WWW browser at client machine 1104 and accesses to the homepage forfacsimile reception at WWW server 1103. The user reads out an image datafile at client machine 1104 via the network from WWW server 1103.

A user performs the following operation in the case of performingsimultaneous transmission of the image data that is downloaded at clientmachine 1104 to a plurality of other terminals. In the case ofsimultaneous transmission to a terminal as a G3 facsimile apparatus, theuser transfers image data from client machine 1104 to a printer, setsthe printed imaged data output from the printer at a facsimileapparatus, enters telephone numbers of simultaneous transmissiondestinations, and pushes a transmission button. In addition, in the caseof simultaneous transmission to a terminal as an e-mail apparatus, theuser sets a plurality of e-mail addresses of simultaneous transmissiondestinations as destinations using e-mail software, attaches the imagedata to an e-mail and pushes a transmission button.

However, in the system using the above-described internet FAX and WWWserver, a simultaneous transmission of image data stored at the WWWserver to other terminals results in a problem that network traffic isincreased because the image data should be transferred between theinternet FAX and the e-mail server, between the e-mail server and theWWW server and between the WWW server and the client machine.

SUMMARY OF THE INVENTION

An object of the present invention is to provide a network facsimileapparatus and transmission method capable of decreasing network trafficcaused by data transmission and also of performing simultaneoustransmission easily only by an instruction from a client machine.

The present invention provides a network facsimile apparatus which isable to communicate using both a telephone network and a computernetwork, and has a facsimile section which transmits and receives animage via the public switched telephone network, a mail section whichtransmits and receives an e-mail via the computer network, a web serverwhich transmits a response to a client corresponding to a request fromthe client that is connected to the network apparatus via the computernetwork, a storage which stores received data including an imagereceived by the facsimile section and data of an e-mail received by themail section, and a structured document generating section whichgenerates a structured document containing a description to requestpredetermined processing to the web server from the client, in which theweb server has a transmission section which transmits the received datastored at the storage and the structured document generated by thestructured document generating section to the client corresponding to arequest from the client, and an interface which provides a receivedtransmission request to the facsimile section or the mail section.Accordingly, when the network facsimile apparatus receives atransmission request from a client, the web server provides a structureddocument in homepage format corresponding to the transmission request,and the mail section or facsimile section transmits received data storedat the storage to a predetermined destination based on client entereddata or selected item.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects and features of the invention will appearmore fully hereinafter from a consideration of the following descriptiontaken in connection with the accompanying drawing wherein one example isillustrated by way of example, in which;

FIG. 1 is a configuration diagram of facsimile transmission andreception system using a FAX server;

FIG. 2 is a configuration diagram of facsimile transmission andreception system using an internet FAX and a WWW server;

FIG. 3 is a function block diagram of a network facsimile apparatusaccording to an embodiment of the present invention;

FIG. 4 is a configuration diagram of a system in which the networkfacsimile apparatus according to the above embodiment is connected to aclient machine;

FIG. 5 is a function block diagram illustrating a flow of a part ofprocessing in the network facsimile apparatus according to the aboveembodiment;

FIG. 6 is a flowchart of an operation to generate a reception list froma reception in the network facsimile apparatus according to the aboveembodiment;

FIG. 7 is a structure diagram of a reception list management table;

FIG. 8 is a diagram illustrating a data example of a source file of areception list html;

FIG. 9 is a flowchart of an operation for transmitting data received andstored at the network facsimile apparatus according to the aboveembodiment;

FIG. 10 is a diagram illustrating a file relation table of HTML filesmanaged by the network facsimile apparatus according to the aboveembodiment;

FIG. 11 is a structure diagram of a homepage main page provided by thenetwork facsimile apparatus according to the above embodiment;

FIG. 12 is a structure diagram of an internet received document pageprovided by the network facsimile apparatus according to the aboveembodiment;

FIG. 13 is a flowchart illustrating an operation performed until atransmission is finished in the network facsimile apparatus according tothe above embodiment;

FIG. 14 is a structure diagram of a send instruction page provided inthe above embodiment;

FIG. 15 is a flowchart illustrating an operation of WWW servercommunication section in the network facsimile apparatus according tothe above embodiment;

FIG. 16 is a flowchart illustrating transmission processing in thenetwork facsimile apparatus according to the above embodiment;

FIG. 17 is a structure diagram of a user setting page provided in theabove embodiment;

FIG. 18 is a flowchart of device setting processing in the networkfacsimile apparatus according to the above embodiment; and

FIG. 19 is a structure diagram of a communication result report pageprovided in the above embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The embodiment of the present invention will be described below indetail with reference to drawings.

FIG. 3 illustrates a function block diagram of a network facsimileapparatus according to this embodiment. ROM 2, RAM 3 and externalstorage 4 are connected to CPU 1 that operates by an operating systemand is accessible to ROM 2, RAM 3 and external storage 4. Variousprograms such as processing program for a server side are stored at ROM2. RAM 3 is used, for example, as a working area of programs stored atROM 2. Compressed image data and HTML files are stored at externalstorage 4.

In addition, the network facsimile apparatus according to thisembodiment has scanner 5, printer 6, panel section 7,compression/expansion section 8, FAX/speech communication section 9 andnetwork control section 10 which operate under the control of CPU 1.

The network facsimile apparatus performs scanning of image data of, forexample, document by scanner 5, and performs printing of scanned imagedand received imaged data at printer 6. A user is able to performoperations such as an instruction to scan image data and an input ofdestination address using panel section 7. Compression/expansion section8 performs expansion of received image data and compression of scannedimage data. FAX/speech communication section 9 performs facsimilecommunication and speech communication connecting to a PSTN. Networkcontrol section 10 performs the internet communication connecting to anetwork.

The programs stored at ROM 2 include each program for HTML filegenerating section 11, WWW server section 12, e-mail communicationsection 13 and TIFF conversion section 14. Although each function ofHTML file generating section 11, WWW server section 12, e-mailcommunication section 13 and TIFF conversion section 14 is providedunder the respective program executed by CPU 1, the respective functionwill be described using respective numeral symbol provided to therespective program as illustrated in FIG. 3 as a matter ofaccommodation.

HTML file generating section 11 converts lists of image data received byfacsimile and e-mail and other data into HTML files readable on ahomepage to register to a server.

WWW server section 12 provides a server function of, for example,performing communication with a WWW browser in accordance with HTTP(Hyper Text Transfer Protocol) to exchange homepage data (HTML file).

E-mail communication section 13 performs transmission and reception ofe-mail via a network, while functions as an e-mail server. In addition,TIFF conversion section 14 provides a function of converting codedfacsimile data and document file data into TIFF (Tag Images File Format)format that is a standard format for image files. In the case oftransmitting image data scanned by scanner 5 or facsimile data stored atexternal storage 4 by e-mail, the data is converted into a file in TIFFat TIFF conversion section 14, and an e-mail containing the TIFF file asan attached file is generated. In other words, the TIFF file istext-coded and input to a multiple structured mail data section for,such as, MIME (Multipurpose Internet Mail Extensions). On the otherhand, in the case of facsimile transmission of e-mail received data, ane-mail is converted from text code into TIFF file by binary conversion.TIFF conversion section 14 opens the TIFF file. When the TIFF file isnot compressed, the data further subjected to compression processingsuch as MH (Modified Huffman) at compression/expansion section 8 istransmitted.

FIG. 4 illustrates a system configuration in the case of connecting anetwork facsimile apparatus according to this embodiment to a PSTN and anetwork. In FIG. 4, network facsimile apparatus 201 is connected to thePSTN while connected to the network through a network interface. It ispossible to browse a homepage provided at network facsimile apparatus201 by operating a WWW browser at client machine 202.

FIG. 5 illustrates a function block diagram for HTML file generatingsection 11, WWW server section 12, e-mail communication section 13, TIFFconversion section 14 and FAX/speech communication section 9 and a flowof data processing between the blocks.

In WWW server section 12, WWW server communication section 31communicates with a WWW browser operating at client machine 202 inaccordance with HTTP protocol. A command received at www servercommunication section 31 from client machine 202 is analyzed at CGIstring analysis section 32.

CGI string analysis section 32 analyzes a CGI (Common Gateway Interface)string contained in received data and provides the analyzed result toCGI application deciding section 33. Based on the analyzed result, CGIapplication deciding section 33 starts corresponding CGI application 34.CGI application 34 executes a predetermine processing using the receiveddata. CGI application 34 includes applications for, for example,transmission, processing such as delete, edit and move for HTMLdocument, generation of address book, and device setting.

File providing section 35 receives a file, whose file request isprovided from client machine 202, from file management section 36 toprovide to WWW server communication section 31. When the file requestdoes not requires the CGI processing, file providing section 35 requiresa corresponding file to file management section 36.

HTML file generating section 11 has document list generating section 37that generates a HTML file of document list and address book generatingsection 38 that generates a HTML file of address book.

Document list generating section 37 generates a HTML file of receptionlist indicative of received e-mail and received FAX and performs adelete, edit and move of a part of the HTML file according to aninstruction provided from CGI application 34 and received data.

Address book generating section 38 modifies the HTML file of addressbook according to an instruction from the address book CGI applicationand received data. Further, address book generating section 38 executesprocessing to incorporate the latest address table data into the HTMLfile of address book when power is turned on and the content of theaddress book is changed.

In addition, HTML file generating section 11 has communication resultlist generating section 39 and status information generating section 41.Communication result list generating section 39 receives log informationindicative of communication result from FAX/speech communication section9 and e-mail communication section 13 to generate and update the HTMLfile indicative of the communication result list. Status informationgenerating section 41 reads out status signals indicative of respectivestatus from scanner 5, printer 6, panel section 7 and FAX/speechcommunication section 9 (for example, eruption of paper stack, lack oftoner and on-communication) to generate and update a HTML file in whichthe respective statuses are registered.

FAX/speech communication section 9 has spooler 42, communication controlsection 43 and storage processing section 44. Spooler 42 receives aninstruction of transmission processing, transmission document number ortemporary document, FAX number of destination terminal and others fromthe transmission CGI application. When the transmission document numberis provided, FAX/speech communication section 43 reads out transmissiondata (image) of the corresponding document number from external storage4. Communication control section 43 inputs the image data provided fromspooler 42 to a transmission buffer, and then connects to the PSTN totransmit to a FAX number of destination terminal. In the case ofsimultaneous transmission, a plurality of FAX numbers that aresimultaneous transmission destinations are spooled from the transmissionCGI to spooler 42.

E-mail communication section 13 has spooler 45, communication, controlsection 46 and storage processing section 47. Spooler 45 receives aninstruction of transmission processing, transmission document number ortemporary document, mail address of destination terminal and others fromthe transmission CGI application. When the transmission document numberis provided, FAX/speech communication section 43 reads out transmissiondata of the corresponding document number from external storage 4.Communication control section 46 inputs the image data provided fromspooler 45 to a transmission buffer, and then connects to a network suchas the internet using LAN or dial-up to transmit to an e-mail address ofdestination terminal. In the case of simultaneous transmission, aplurality of e-mail addresses that are simultaneous transmissiondestinations are spooled from the transmission CGI application tospooler 45.

The operation of the network facsimile apparatus according to thisembodiment will be described next. Hereinafter, each operation ofgeneration of reception list, simultaneous transmission of stored data,device setting and generation of communication result report will bedescribed separately.

FIG. 6 illustrates a flowchart of an operation to generate a receptionlist from a data reception. The network facsimile apparatus registersthe reception list of received data received at FAX/speech communicationsection 9 and e-mail communication section 13 to a homepage.

When a data reception occurs, it is decided whether the reception of thereceived data is performed via the PSTN or the internet (ST401). Whene-mail communication section 13 receives an e-mail, the reception isperformed via the internet. In this case, e-mail communication section13 receives the e-mail (ST402). When attached data of the e-mail isimage data in TIFF format, e-mail communication section 13 stores theimage data at external storage 4 providing a file name such as, forexample, “mail0001.tif” (ST407). When attached data is speech data,e-mail communication section 13 stores the speech data at externalstorage 4 providing a file name such as, for example, “audio0001.wav”(ST407).

On the other hand, when FAX/speech communication section 9 receives FAXdata or speech data, the reception is performed via the PSTN. In thiscase, FAX/speech communication section 9 receives image data or speechdata (ST403), and decides whether or not the reception data is speechdata (ST404). When the received data is coded image data, FAX/speechcommunication section 9 requests TIFF conversion section 14 to convertthe coded data into TIFF format (ST405). FAX/speech communicationsection 9 provides a file name (for example, “fax0001.tif”) to theTIFF-converted received data to store at external storage 4 (ST407).When the received data is speech data, FAX/speech communication section9 converts the speech data into digital data (ST406) and stores thespeech file provided with a file name at external storage 4 (ST407).

The processing for generating a communication result report, which willbe described later, is next executed (ST408). It is decided whether ornot the setting indicates only printing referring to the device setting(ST409). FAX/speech communication section 9 and e-mail communicationsection 13 fetch device setting data indicative of handling of receiveddata from external storage 4 when power is turned on to store. When thesetting indicates only printing, FAX/speech communication section 9 ande-mail communication section 13 convert the received data into printableformat to provide to printer 6 along with an instruction for printing(ST410). After printing processing, FAX/communication section 9 ande-mail communication section 13 instruct file management section 36 todeleted the corresponding received data (ST411). On the other hand, whenthe setting does not indicate only printing, it is decided whether ornot the setting indicates only storage (ST412). In the case of providinga download of received data to client machine 202, since it is onlynecessary to store the received data without printing, it is possible todesignate “only storage” as a device setting. When the setting indicatesonly setting, FAX/communication section 9 and e-mail communicationsection 13 execute the processing for generating a reception listwithout printing processing (ST413). In addition, when the setting doesnot indicate only storage, FAX/communication section 9 and e-mailcommunication section 13 instruct printing processing (ST413), and thengenerate a reception list (ST414).

The reception list generating processing at ST414 is achieved by thatHTML file generating section 11 adds a file name to the reception listand updates the HTML file of the reception list.

The update of the HTML file of reception list will be describedspecifically. Document list generating section 37 at HTML filegenerating section 11 updates the HTML file of reception list. Documentlist generating section 37 manages a reception list table stored atexternal storage 4. FIG. 7 illustrates an example of a structure of areception list management table. In the reception list management table,document numbers, document file names, registered data, senders andtitles are registered, in which the document number is provided in orderof reception and the other items are registered for every documentnumber.

Document list generating section 37 receives the document file name,registered data, sender and title from FAX/speech communication section9 or e-mail communication section 13 that receives the correspondingdata. Document list generating section 37 reads out the reception listthrough file management section 36, adds the document number to thereception list, and registers the document file name, registered data,sender and title to the reception list. Document list generating section37 returns the reception list in which the document name and the otheritems of the received data are registered to the reception list table,while reads out a reception list html (HTML file of reception list).Document list generating section 37 adds the received data which isnewly registered to the reception list to reception list html.

FIG. 8 illustrates a source file of reception list html generated withrespect to the received data via a network. As illustrated in FIG. 8, acomment line is inserted at a head for every reception list.Identification data indicative of reception form and a document numberare described at the position of the comment line. The comment line isfollowed by a document number, data, sender and title that are describedin HTML document.

In addition, with respect to FAX reception list concerning FAX receivedimage data and speech reception list concerning received speech data,the lists are similarly generated in HTML document.

As described above, when FAX/speech communication section 9 receives FAXdata or e-mail communication section 13 receives an e-mail, thecorresponding section inputs data necessary for the list generation (forexample, sender and title) document list generating section 37. Documentlist generating section 37 reads out the HTML file of reception listfrom external storage 4 and adds those data to the reception list.Therefore, client machine 202 is able to obtain a supply of the latestreception list in homepage format by accessing to WWW server section 12.

An operation of transmitting data received and stored at the networkfacsimile apparatus to client machine 202 will be described nextaccording to a flowchart in FIG. 9.

The network facsimile apparatus is in a stand-by state until a homepageaddress (URL address) is input.

Client machine 202 connected to a network starts a WWW browser (homepagebrowsing software) and inputs the URL address of the network facsimileapparatus to access the homepage (ST701).

In the network facsimile apparatus accessed, WWW server section 12initiates the processing through network control section 10. Fileproviding section 35 at WWW server section 12 responds to a command forrequesting a file of the homepage main page (index html) received fromclient machine 202 and reads out the corresponding file from externalstorage 4 to return to the WWW browser at client machine 202 (ST702).FIG. 10 illustrates a file relation table of the HTML files registeredat external storage 4. The files needed to display the homepage arerelated to the file of homepage main page.

When the WWW browser at client machine 202 receives the file of homepagemain page, the WWW browser analyzes the content and transmits a commandfor requesting the files needed to display the homepage to WWW serversection 12 (ST703). For example, when the homepage main page illustratedin FIG. 11 is displayed, the WWW browser at client machine 202 requestsfiles necessary for respective icon display of facsimile receiveddocument, internet received document, personal box, bulletin boarddocument, address book, communication result report, user setting andsetting list (sdoc.gif, kdoc.gif, etc. illustrated in FIG. 10) to WWWserver section 12.

When WWW server section 12 receives the request of files needed todisplay the homepage main page, WWW server 12 section transmits thefiles stored at external storage 4 to the WWW browser at client machine202 (ST704). Thus, the homepage of the network facsimile apparatus isdisplayed on a screen of client machine 202 (ST705). The networkfacsimile apparatus stands by until next selection is performed.

The network facsimile apparatus awaits until an icon that is desired bya user is selected on the main page illustrated in FIG. 11 displayed atclient machine 202. For example, assume that an “internet receptionlist” icon is selected among from displayed data. When the “internetreception list” icon is selected, a file request is generated for theinternet reception list that is linked to a display position of the icon(ST706).

As illustrated in FIG. 10, the icon of “internet reception list”(idoc.gif) is linked to the HTML file of internet received document page(idoc.html). The WWW browser is able to display the internet receptionlist using a file of idoc.html. When WWW server section 12 receives thefile request for idoc.html, WWW server section 12 reads out thecorresponding file from external storage 4 to transmit to client machine202 (ST707).

The WWW browser at client machine 202 displays a page of “internetreception list” (internet received document page) according to the HTMLfile of “internet reception list” received from WWW server section 12(ST708).

FIG. 12 illustrates a structure example of an internet received documentpage. In the internet received document page illustrated in FIG. 12,document numbers of received data registered in the reception list,check buttons for selecting each document number and information relatedto of each document are displayed. Further, a frame menu includingtransmission processing is displayed. Each frame of the frame menuillustrated in FIG. 12 is related to another file for executing theprocessing corresponding to the menu (for example, transmission).

A user selects a desired document number on the internet receiveddocument page at client machine 202 (ST709). The network facsimileapparatus to which a file of the selected document number is requestedtransmits the corresponding image data file (ST710). However, there isthe case where client machine 202 does not display a downloaded filedepending on file format. For example, in the case where a TIFF file isdownloaded at client machine 202 which is not able to display a TIFFfile, a helper application to display the TIFF file is started (ST712).The TIFF file is displayed using the helper application (ST713).

The aforementioned example describes about the case of displaying datareceived via a network. However, when a speech file is selected, thespeech data linked to the speech file is played back at a speaker ofclient machine 202. The speech data includes speech data that the userrecords at a receiver of the network facsimile apparatus besides thespeech data received from outside, and it is possible to link thesespeech data to the homepage and also to transmit toward outside.

The operation of the case of performing simultaneous transmission in thenetwork facsimile apparatus will be described next. FIG. 13 illustratesa series of flowchart from a step where client machine 202 instructs asimultaneous transmission to the network facsimile apparatus to anotherstep where the simultaneous transmission is performed to destinations.

In FIG. 13, the processing of ST701 to ST708 is the same as described inFIG. 9, where client machine 202 accesses to the network facsimileapparatus using URL, and then a reception list is displayed.

Assume that an internet received document is displayed at client machine202 at ST708. A user selects a document number to be subjected tosimultaneous transmission among from internet received documentsillustrated in FIG. 12 (ST1102). In addition, in the case of selectingFAX received data among from received data stored at the networkfacsimile apparatus to transmit (including simultaneous transmission) toanother terminal, a FAX received document page is displayed as areception list. The FAX received document page is composed in thesimilar way with the internet received document.

On the internet received document page, when a user selects a checkbutton corresponding to a document number to be subjected totransmission and pushes down a send button, the selected document numberis held at client machine 202, while a file request is provided for asend instruction page file (pnl.snd.html) linked related to the sendbutton as illustrated in FIG. 10 (ST1102). The HTML document composingthe internet received document page is linked to the send instructionpage file (pnl.snd.html) through the send button.

WWW server section 12 reads out the send instruction page file fromexternal storage 4 in responses to the file request for the sendinstruction page file (pnl.snd.html), and transmits the file to clientmachine 202 (ST1103). Client machine 202 receives the send instructionpage file from WWW server 12 and opens a window of the send instructionpage (ST1104).

FIG. 14 illustrates a structure of the send instruction page displayedaccording to the send instruction page file. The send instruction pagehas a document number of the received data to transmit, a box to input adestination FPX number and another box to input a destination e-mailaddress.

A user enters data necessary for transmission (document number,facsimile number, e-mail address and others) at ST1105, while thedocument number to be transmitted which is selected at ST1101 and storedis automatically entered into a document number box. When a destinationterminal is a facsimile apparatus, the user enters a facsimile numberinto a destination facsimile number. When a destination terminal is ane-mail apparatus, the user enters a destination e-mail address into adestination e-mail address.

In addition, a user is able to enter a facsimile number and e-mailaddress using an address book. The address book is stored at HTML formatat external storage of the network facsimile apparatus, is downloadedfrom the network facsimile apparatus by pushing a reload button and isdisplayed on the send instruction page to select.

In the case of simultaneous transmission to a plurality of terminals, auser enters a plurality of facsimile numbers or e-mail addressesrespectively into a facsimile number box or e-mail address boxseparating those addresses with comma. A plurality of document numbersare also entered with comma inserted between the document numbers whenthe plurality of document numbers are selected at ST1101.

When a user enters both FAX number and e-mail address, the simultaneoustransmission is performed to the facsimile apparatus and e-mailapparatus. When a user enters either of FAX number or e-mail addressnumber, an ordinary facsimile transmission or e-mail transmission isperformed.

When a user pushes down a determine-button provided on the sendinstruction page illustrated in FIG. 14, a CGI processing request istransmitted to WWW server section 12 (ST1106). According to the CGIprocessing request, a CGI string for instructing a send CGI application,the document number entered on the send instruction-page, and facsimilenumber or e-mail address are URL encoded and transmitted to WWW serversection 12.

WWW server section 12 transmits the designated document to a designateddestination by executing the send CGI application in response to the CGIprocessing request (ST1107). WWW server section 12 further transmits thefinished file to client machine 202 after the transmission is finished(ST1107). Client machine 202 receives the finished file and performs acompletion display (ST1108).

FIG. 15 illustrates a schematic operation performed until the CGIapplication is executed in WWW server section 12. WWW servercommunication section 31 receives a request from client machine 202 viaa network and returns a response, while operating in accordance withHTTP protocol. The requests which WWW server communication section 31receives are separated into principally two; file request and CGIprocessing request corresponding to command.

The received data (request) received at WWW server communication section31 is provided to CGI string analysis section 32. CGI string analysissection 31 analyzes a CGI string of the received data, and decideswhether or not the received data is a CGI processing request (ST1300).When the received data is not the CGI processing request, but is a filerequest, the received data does not contain a CGI string. In this case,file providing section 35 reads out the corresponding file from externalstorage 4 based on a document number contained in the received data totransmit to client machine 202 (ST1301).

On the other hand, when received data is a CGI processing request, CGIstring analysis section 32 decodes a URL encoded part of the receiveddata (ST1302). The decoded data that is a analyzed result of the CGIstring is provided to CGI application deciding section 33. CGIapplication deciding section 33 decides whether or not an applicationname is designated (ST1303), and makes an error decision when theapplication name is not designated (ST1304). When the error decision ismade, CGI application deciding section 33 provides an error notificationto file providing section 35. File providing section 35 reads out a HTMLfile for error notification from external storage 4 to transmit toclient machine 202 (ST1305).

When an application name is designated in the decoded data, CGIapplication deciding section 33 decides a CGI application designated inthe CGI string. When CGI application deciding section 33 decides that asend CGI application is designated in the CGI string (ST1306), CGIapplication deciding section 33 starts the send CGI application toprovide the received data, and transmission processing which will bedescribed later is executed (ST1307). When CGI application decidingsection 33 decides that a device setting CGI application is designatedin the CGI string (ST1308), CGI application deciding section 33 startsthe device setting CGI application to provide to the received data, anddevice setting processing which will be described later is executed(ST1309).

When other CGI application supported by WWW server section 12 of thisembodiment is designated, a respective CGI application is executed eventhough the other CGI applications are not shown in FIG. 15.

FIG. 16 illustrates a flowchart of transmission processing (ST1307) inthe network facsimile apparatus. The send CGI application receivesreceived data containing a document number and a destination facsimilenumber or e-mail address that are received from client machine 202 fromCGI application deciding section 33.

The send CGI application decides whether or not there are a plurality ofdocuments to be transmitted at a single transmission (ST1401). When aplurality of document numbers are selected from a reception list atST1101 described above (FIG. 13) or a plurality of document numbers areentered into the document number box at ST1105, the send CGI applicationdecides that a plurality of documents are designated by a decision madeat ST1401.

When a plurality of document numbers are designated on the sendinstruction page, the send CGI application merges transmission datacorresponding to each document number into a single document (St1402).Since a plurality of documents are merged into a single document, it ispossible to transmit a plurality of designated documents at a singlecommunication. The merged document is treated as a temporary document.The merging processing is not necessary when a single document isdesignated.

The send CGI application decides whether a transmission to a destinationterminal should be performed by facsimile or e-mail. Specifically, thesend CGI application decides whether or not a facsimile number isentered into the facsimile number box on the send instruction page(ST1403). When a facsimile number is entered, the send CGI applicationexecutes a facsimile transmission (ST1404).

A procedure of facsimile transmission will be described specifically.The send CGI application transfers a temporary document and a facsimilenumber, further a command for facsimile transmission to spooler 42 atFAX/speech communication section 9. In the case of simultaneoustransmission, a plurality of facsimile numbers are spooled at spooler42. Spooler 42 provides an storage address of the temporary document andfacsimile number to communication control section 43. In the case ofsimultaneous communication, spooler 42 provides a plurality of spooledfacsimile numbers one by one along with the storage address of temporarydocument to communication control section 43. Communication controlsection 43 connects to the facsimile number provided from spooler 42 viathe PSTN and transmits the temporary document by facsimile. Thetemporary document is deleted after the data transmissions to alldestinations are completed.

In addition, when a plurality of documents are not designated on thesend instruction page, a temporary document is not generated. When adesignated document is one, the document number is input to spooler 42.In this case, spooler 42 reads out a document corresponding to adesignated document number from external storage 4 through filemanagement section 36.

As described above, a setting whether to save a transmitted document atexternal storage 4 is registered at a ROM, and the setting data isloaded at memories of FAX/speech communication 9 and e-mailcommunication section 13 when power is turned on. When the above settingindicates “delete”, spooler 42 instructs file management section 36 todelete the corresponding file from external storage 4.

Communication control section 43 notifies communication result listgenerating section 39 at HTML file generating section 11 of atransmission result (normal termination or abnormal termination) as loginformation when a facsimile transmission is finished. Communicationresult list generating section 39 adds the received log information to acommunication result list (ST1405). Specifically, communication resultlist generating section 39 reads out a communication result filegenerated in HTML document from external storage 4 and adds the loginformation to the communication result file to store at externalstorage 4 when receives the log information.

After the aforementioned facsimile transmission processing is finished,e-mail transmission processing is executed. In the e-mail transmissionprocessing, the send CGI application decides whether or not an e-mailaddress is entered in the e-mail address box on the send instructionpage (ST1406). When an e-mail address is entered, the send CGIapplication executes the e-mail transmission (ST1407). When the e-mailaddress is not entered, an e-mail transmission is not executed becausean e-mail apparatus is not designated as a destination terminal.

The send CGI application provides a storage address of a temporarydocument or a document number, and an e-mail address to spooler 45 ate-mail communication section 13 by the same procedure as theabove-described facsimile transmission. In the case of e-mail, the sendCGI application is able to transmit to a plurality of e-mail addressesat a single communication. Accordingly, in the case of simultaneoustransmission, spooler 45 provides all e-mail addresses to communicationcontrol section 46 at a single time. In addition, when a document otherthan TIFF format is designated, the send CGI application converts thedocument into TIFF format to transmit.

Communication control section 46 notifies communication result listgenerating section 39 at HTML file generating section 11 of acommunication result as log information when the e-mail transmission isfinished. Communication result list generating section 39 adds thereceived log information to a communication result list (ST1408).

In addition, when a facsimile number and an e-mail address both areentered, the send CGI application executes respective processing for theabove-described facsimile transmission and e-mail transmission.

When the processing for facsimile transmission and e-mail transmissionis finished as described above, the send CGI application transmits aHTML file of processing completion message to client machine 202(ST1409). Specifically, the send CGI application inputs destinationinformation (facsimile number and e-mail address) and a temporarydocument (storage address) or document number to spooler 42 and 45,requests the HTML file of processing completion message to filemanagement section 36, and provides a transmission request of thecorresponding file to file providing section 35.

According to the aforementioned processing, client machine 202 whichprovides the CGI processing request is able to receive the HTML file ofprocessing completion message and is also able to notify a user ofprocessing completion by displaying the message.

The operation for setting a handling (print or save) of FAX receiveddocument and network received document will be described next. When auser selects a “user setting” icon on the homepage main page at ST706described previously, client machine 202 issues a file requestconcerning a HTML file linked to the “user setting” icon to WWW serversection 12. In WWW server section 12 which receives the file requestconcerning the HTML file for user setting, file providing section 35reads out corresponding user setting html from external storage 4 totransmit to client machine 202.

In client machine 202, the WWW browser displays a user setting pageusing the user setting html. FIG. 17 illustrates a structure example ofuser setting page. On the user setting page, a user is able to set threedifferent patterns concerning a handling of received document for everyFAX received document and network received document. The three patternsare (a) printing only, (b) saving only, and (c) printing and saving.Further, the user setting page is composed in order to enable a user toset a storage period of document for every FAX received document andnetwork received document. In an example illustrated FIG. 17, storageperiods are separated into 1 day, 1 week and 1 month, however it may bepossible to compose the page in order to enable a user to set anystorage period. When a user selects a document type, a handling type ofa document and a storage period and then selects a determine-button, thesetting data is transmitted to WWW server section 12 along with a CGIprocessing request for a device setting CGI application.

In WWW server section 12, CGI application deciding section 33 starts thedevice setting CGI application to provide the received setting data.FIG. 18 illustrates a flowchart of device setting processing concerninga setting of received document. The device setting CGI applicationreceives the setting data concerning a setting of received document,which is received from client machine 202, from CGI application decidingsection 33.

The device setting CGI application decides for every FAX receiveddocument and network received document whether or not the setting dataindicates (a) only printing (ST1601). When a setting for any receiveddocument indicates (a) only printing, the device setting CGI applicationsets 1 on a flag of a setting table of the received document (ST1602).Flag=1 indicates a setting for (a) only printing. When a setting for anydocument does not indicate (1) only setting, the device setting CGIapplication decides whether or not the setting indicates (b) only saving(ST1603). When a setting for any received document indicates (b) onlysaving, the device setting CGI application sets 2 on a flag of a settingtable of the received document (ST1604). Flag=2 indicates a setting for(b) only saving. When the setting data does not indicate any cases ofST1601 and ST1603, the device setting CGI application sets 3 on a flagof a setting table of the received document (ST1605). Flag=3 indicates asetting for (b) printing and saving.

The device setting CGI application provides the setting table in whichthe flag is set to file management section 36. File management section36 stores the setting table at external storage 4. File managementsection 36 reads a memory area of external storage 4 at which thesetting table is stored when power is turned on, and loads the settingtable to spoolers 42 and 45.

In addition, the device setting CGI application registers setting dataof a setting of document storage period in the same way as describedabove, and stores the setting table at external storage 4. The devicesetting CGI application loads the setting data of storage period to filemanagement section 36 when power is turned on and refers to the settingdata periodically to delete a corresponding document.

As described above, since the network facsimile apparatus displays ahandling of document and document storage period on a HTML document pagedesignated by a user at client machine 202 in response to a request fromclient machine 202 and provides the user entered data and device settingdesignation to WWW server section 12 in order to reflect in a settingtable. According to the above processing, a user is able to set ahandling of document and document storage period in the same operationas accessing to a homepage using client machine 202.

In addition, when a user selects a “communication result report” icon ona homepage main page at ST706 described previously, a file request for acommunication result html linked to the “communication result report” isissued to WWW server section 12 from client machine 202. In WWW serversection 12 which receives the file request for a HTML file forcommunication result report, file providing section 35 reads out thecorresponding communication result report html from external storage 4to transmit to client machine 202.

In client machine 202, the WWW browser displays a page of usercommunication result report using the communication result html. FIG. 19illustrates a structure example of communication result report page. Thenetwork facsimile apparatus inputs a transmission result and receptionresult as a form of log information to communication result listgenerating section 39 when facsimile communication and/or e-mailcommunication is performed. Communication result list generating section39 always updates communication result html based on the log-informationindicative of the transmission result and reception result. Accordingly,the latest communication result is displayed by generating acommunication result report based on the communication result html. Thecommunication result includes a reception number that is providedserially to transmission data and received data, communication data,communication partner, a number of sheets, communication type(transmission or reception), communication duration time, mode andcommunication condition.

As described above, since a communication result report is generated inHTML document and the generated report is linked to a homepage mainpage, a user is able to know the communication result easily at clientmachine 202.

As described above in detail, the present invention is able to provide anetwork facsimile apparatus capable of decreasing network traffic causedby data transmission and of transmitting stored data to any destinationsonly by a transmission instruction from a client side.

The present invention is not limited to the above described embodiments,and various variations and modifications may be possible withoutdeparting from the scope of the present invention.

This application is based on the Japanese Patent Application No.HEI11-18998 filed on Jan. 27, 1999, entire content of which is expresslyincorporated by reference herein.

1. A communication apparatus connected to a terminal apparatus via anetwork, the communication apparatus comprising: an e-mail receiver thatperforms an e-mail reception via the network; a facsimile receiver thatperforms a facsimile reception via a telephone network; a file generatorthat generates an HTML file for a web page indicating a result of thee-mail reception performed by the e-mail receiver and a result of thefacsimile reception performed by the facsimile receiver, wherein theresult indicates whether the e-mail reception was a success or a failureand whether the facsimile reception was a success or a failure; astorage that stores the HTML file generated by the file generator; and aweb server that transmits the HTML file to the terminal apparatus viathe network so that the web page is displayed at the terminal apparatus.2. The communication apparatus according to claim 1, wherein the webpage indicates a communication partner of the e-mail reception.
 3. Thecommunication apparatus according to claim 1, wherein the web pageindicates a time and date of the e-mail reception.
 4. The communicationapparatus according to claim 1, further comprising a memory that storesa file attached to an e-mail received in the e-mail reception.
 5. Thecommunication apparatus according to claim 1, wherein the web pageindicates a communication partner of the facsimile reception.
 6. Thecommunication apparatus according to claim 1, wherein the web pageindicates a time and date of the facsimile reception.
 7. Thecommunication apparatus according to claim 1, further comprising aconverter that converts facsimile data received in the facsimilereception into image data and a memory that stores the converted imagedata.
 8. The communication apparatus according to claim 1, the HTML filebeing configured for transmission to the terminal apparatusindependently of the transmission of the e-mail or of the facsimile to adestination.
 9. The communication apparatus according to claim 1,wherein the storage stores a web page including a mark indicating arequest for the result of the reception, and the web server transmitsthe web page to the terminal apparatus in response to an actuation ofthe mark, wherein the request for the result of the reception isperformed by clicking the mark on the web page at the terminalapparatus.
 10. A communication result informing method that informs aterminal apparatus of a result of a communication by a communicationapparatus connected to the terminal apparatus via a network, thecommunication result informing method comprising: performing an e-mailreception via the network; performing a facsimile reception via atelephone network; generating an HTML file for a web page indicating aresult of the e-mail reception performed and a result of the facsimilereception performed wherein the result indicates whether the e-mailreception was a success or a failure and whether the facsimile receptionwas a success or a failure; storing the generated HTML file; andtransmitting the HTML file to the terminal apparatus via the network sothat the web page is displayed at the terminal apparatus.
 11. Thecommunication result informing method according to claim 10, wherein theweb page indicates a communication partner of the e-mail reception. 12.The communication result informing method according to claim 10, whereinthe web page indicates a time and date of the e-mail reception.
 13. Thecommunication result informing method according to claim 10, furthercomprising storing a file attached to an e-mail received in the e-mailreception.
 14. The communication result informing method according toclaim 10, wherein the web page indicates a communication partner of thefacsimile reception.
 15. The communication result informing methodaccording to claim 10, wherein the web page indicates a time and date ofthe facsimile reception.
 16. The communication result method accordingto claim 10, further comprising converting facsimile data received inthe facsimile reception into image data and storing the converted imagedata.
 17. The communication result informing method according to claim10, wherein the HTML file is configured for transmission to the terminalapparatus independently of the transmission of the e-mail or thefacsimile to a destination.
 18. The communication result informingmethod according to claim 10, further comprising storing a web pageincluding a mark indicating a request for the result of the reception,and the transmitting transmits the web page to the terminal apparatus inresponse to an actuation of the mark, wherein the request for the resultof the reception is performed by clicking the mark of the web page atthe terminal apparatus.